Node-RED block in Snap4City Microservice library node-red-contrib-snap4city-developer is "service-search-near-service">
    <p>It allows to retrieve the set of services that are near a given service identified by its serviceUri. The services can
        be filtered as belonging to specific categories (e.g. Accomodation, Hotel, Restaurant etc), model or value. </p>

    <h3>Inputs</h3>
    A JSON with these parameters:

     <dl class="message-properties">
		 <dt>typeQuery
				<span class="property-type">string</span>
			</dt>
			<dd> If "point-of-interest" is selected, the system will perform a search of the data contained in the Knowledge Base (KB) if, on the other hand, the user selects "entity," the system will perform a search using iot-search.</dd>
        <dt>serviceuri
            <span class="property-type">string</span>
        </dt>
        <dd> serviceUri (http://...) of the service (<a target="_blank" href="https://www.snap4city.org/drupal/node/737">info about ServiceUri</a>)</dd>
        <dt>filter
            <span class="property-type">string</span>
        </dt>
        <dd>Only for the type "entity", a list of conditions (separated with ;) on value names matching a constant value. The matching operator can be:
            <ul>
			<li><em>value name</em>:<em>string value</em> (e.g status:Active), search for devices having the dynamic string attribute "value name" with a specific value, the match is case sensitive</li>
			<li><em>value name</em>=<em>numeric value</em> (e.g. temperature=18), search for devices having the dynamic numeric attribute "value name" with a specific numeric value.</li>
			<li><em>value name</em>&gt;<em>numeric value</em> (e.g. temperature&gt;20), search for devices having a dynamic numeric attribute greater than a specific value.</li>
			<li><em>value name</em>&gt;=<em>numeric value</em> (e.g. temperature&gt;20), search for devices having a dynamic numeric attribute greater or equal than a specific value.</li>
			<li><em>value name</em>&lt;<em>numeric value</em> (e.g. temperature&lt;20), search for devices having a dynamic numeric attribute less than a specific value.</li>
			<li><em>value name</em>&lt;=<em>numeric value</em> (e.g. temperature&lt;=20), search for devices having a dynamic numeric attribute less or equal than a specific value.</li>
			</ul>
		If multiple conditions are present they are considered in AND.
		<dt>values
            <span class="property-type">string</span>
        </dt>
        <dd>Only for the type "entity". If filter is not empty, list of value names (separated by ;) to be returned for each result, if omitted all values are returned.</dd>
        <dt>sortOnValue
            <span class="property-type">string</span>
        </dt>
        <dd>Only for the type "entity". If filter is not empty, the value name to sort the result, it can be like "value name:asc|desc:type" (e.g. temperature:desc:short), order direction 
		is "asc" if omitted, type can be string, date, long or short (if type is omitted string is assumed). The type is used to force sorting 
		for dates and numbers. If the parameter is omitted the sort is on the distance from GPS position, if "none" is specified no specific 
		sort is used.</dd>
		<dt>categories
            <span class="property-type">string</span>
        </dt>
        <dd> the list of categories of the services to be retrieved separated with semicolon, if omitted all kinds of services
            are returned. It can contain macro categories or categories, if a macro category is specified all categories
            in the macro category are used. The complete list of categories and macro categories can be retrieved on servicemap.disit.org</dd>
        <dt>model
            <span class="property-type">string</span>
        </dt>
        <dd> search for iot devices created with a specific model name.</dd>	
		
		<dt>maxdistance
            <span class="property-type">number</span>
        </dt>
        <dd> maximum distance from the GPS position of the services to be retrieved, expressed in Km (0.1 is used if parameter
            is missing) if it is equal to “inside” it searches for services with a WKT geometry that contains the specified
            GPS position (e.g a park)</dd>
        <dt>maxresults
            <span class="property-type">number</span>
        </dt>
        <dd> maximum number of results to be returned (if parameter is missing 100 is assumed), if it is 0 all results are returned</dd>
        <dt>lang
            <span class="property-type">string</span>
        </dt>
        <dd> ISO 2 chars language code (e.g. “it”, “en”, “fr”, “de”, “es”) to be used for returned descriptions if available in
            multiple languages. Currently for languages other than “it” and “en” it returns “en” descriptions. (if parameter
            is missing “en” is assumed)</dd>
        <dt>geometry
            <span class="property-type">boolean</span>
        </dt>
        <dd> true/false, if true it returns a “hasGeometry” property for each service stating if the service has a complex WKT
            geometries (linestring, polygon) associated with it (if parameter is missing “false” is assumed)</dd>
    </dl>

    <h3>Outputs</h3>
    <ol class="node-ports">
        <li>ServiceUri Array
            <dl class="message-properties">
                <dd> Returns an array containing the servicesUri of each service found</dd>
            </dl>
        </li>
        <li>GeoJSON Results
            <dl class="message-properties">
                <dd> It returns the services split in three sections (BusStops , SensorSites, Services). Each section is provided
                    as GeoJSON “FeatureCollection”, the results are sorted by distance, additionally in each section the
                    “fullCount” property reports the full number of results available matching the query</dd>
            </dl>
        </li>
        <li> All services together
            <dl class="message-properties">
                <dd> It returns the services merge in Results section</dd>
            </dl>
        </li>
    </ol>

    <h3>Details</h3>
    <p>The node can receive a JSON with the parameters described in the Inputs section and with them generate the output JSON.
        If the values are not present in the input JSON, these are read by those in the configuration. If they are not present
        in either part, an error is generated for the necessary parameters.</p>